Merged
Conversation
This introduces configurable rate limiting with middleware and continuation handling, plus documentation and core tests to validate scheduling and enforcement.
Member
|
@Joelgullander Hey, I think this looks solid. The exception handling policy looks right to me too. The only ask I have is could you lift a base "compliance tests" class for the IRateLimitStore and stick that in Wolverine.ComplianceTests? That'll help us move on to other DBs |
Introduce a reusable IRateLimitStore compliance suite and refactor the SQL Server rate limit tests to use it while retaining the schema creation check.
This was referenced Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Need input here, am I on the right track? @jeremydmiller